home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 1998 November / IRIX 6.5.2 Base Documentation November 1998.img / usr / share / catman / u_man / cat3 / Tk / backgderr.z / backgderr
Text File  |  1998-10-30  |  4KB  |  67 lines
  1.  
  2.  
  3.  
  4. TTTTkkkk____BBBBaaaacccckkkkggggrrrroooouuuunnnnddddEEEErrrrrrrroooorrrr((((3333TTTTkkkk))))                                TTTTkkkk____BBBBaaaacccckkkkggggrrrroooouuuunnnnddddEEEErrrrrrrroooorrrr((((3333TTTTkkkk))))
  5.  
  6.  
  7.  
  8. NNNNAAAAMMMMEEEE
  9.      Tk_BackgroundError - report Tcl error that occurred in background
  10.      processing
  11.  
  12. SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  13.      ####iiiinnnncccclllluuuuddddeeee <<<<ttttkkkk....hhhh>>>>
  14.  
  15.      TTTTkkkk____BBBBaaaacccckkkkggggrrrroooouuuunnnnddddEEEErrrrrrrroooorrrr(_i_n_t_e_r_p)
  16.  
  17. AAAARRRRGGGGUUUUMMMMEEEENNNNTTTTSSSS
  18.      Tcl_Interp   *_i_n_t_e_r_p   (in)      Interpreter in which the error occurred.
  19.  
  20.  
  21. DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  22.      This procedure is typically invoked when a Tcl error occurs during
  23.      ``background processing'' such as executing a Tcl command in response to
  24.      a button press or menu entry invocation.  When such an error occurs, the
  25.      error condition is reported to Tk or to a widget or some other C code,
  26.      and there is not usually any obvious way for that code to report the
  27.      error to the user.  In these cases the code calls TTTTkkkk____BBBBaaaacccckkkkggggrrrroooouuuunnnnddddEEEErrrrrrrroooorrrr with
  28.      an _i_n_t_e_r_p argument identifying the interpreter in which the error
  29.      occurred.  TTTTkkkk____BBBBaaaacccckkkkggggrrrroooouuuunnnnddddEEEErrrrrrrroooorrrr attempts to invoke the ttttkkkkeeeerrrrrrrroooorrrr Tcl command
  30.      to report the error in an application-specific fashion.  If no ttttkkkkeeeerrrrrrrroooorrrr
  31.      command exists, or if it returns with an error condition, then
  32.      TTTTkkkk____BBBBaaaacccckkkkggggrrrroooouuuunnnnddddEEEErrrrrrrroooorrrr reports the error itself by printing a message on the
  33.      standard error file.
  34.  
  35.      TTTTkkkk____BBBBaaaacccckkkkggggrrrroooouuuunnnnddddEEEErrrrrrrroooorrrr does not invoke ttttkkkkeeeerrrrrrrroooorrrr immediately (in some cases    |
  36.      this could interfere with scripts that are in process at the time the    |
  37.      error occurred).  Instead, it invokes ttttkkkkeeeerrrrrrrroooorrrr later as an idle callback. |
  38.      TTTTkkkk____BBBBaaaacccckkkkggggrrrroooouuuunnnnddddEEEErrrrrrrroooorrrr saves the values of the eeeerrrrrrrroooorrrrIIIInnnnffffoooo and eeeerrrrrrrroooorrrrCCCCooooddddeeee       |
  39.      variables and restores these values just before invoking ttttkkkkeeeerrrrrrrroooorrrr.        |
  40.  
  41.      It is possible for many background errors to accumulate before ttttkkkkeeeerrrrrrrroooorrrr is|
  42.      invoked.  When this happens, each of the errors is processed in order.   |
  43.      However, if ttttkkkkeeeerrrrrrrroooorrrr returns a break exception, then all remaining error  |
  44.      reports for the interpreter are skipped.
  45.  
  46.  
  47. KKKKEEEEYYYYWWWWOOOORRRRDDDDSSSS
  48.      background, error, tkerror
  49.  
  50.  
  51.  
  52.  
  53.  
  54.  
  55.  
  56.  
  57.  
  58.  
  59.  
  60.  
  61.  
  62.  
  63.                                                                         PPPPaaaaggggeeee 1111
  64.  
  65.  
  66.  
  67.